This was reported by kjwierenga who provided the fix.

Failing test case (modified from kj's original)

in occurrence_enumerator_spec.rb

describe "for a non-recu...

This is a bug.

Failing spec example:

describe "freebusy problem" do

before(:each) do
  cal = RiCal.parse_string(<<ENDCAL)

BEGIN:VCALENDAR METHOD:PUBLISH VERSI...

Yes, it's a bug. I'm not handling the double-quoted tzid parameter to DTSTART.

I'm opening a ticket.

On Fri, Jul 31, 2009 at 4:20 PM, Reid Thompsonreid.thompson...

---------- Forwarded message ---------- From: Christopher Eckman christopher.eckman@gmail.com
Date: Tue, Jul 21, 2009 at 6:03 AM
Subject: Error in component.rb
...

This problem was caused by an improper property value specification for trigger in the component_property_defs.yml file

New Bug

---------- Forwarded message ---------- From: psm42 pscottmurphy@gmail.com
Date: Mon, Jul 20, 2009 at 9:31 AM
Subject: [RiCal] Problem with trigger pars...

excellent, thank you

Forgot to close this. Fix was in 0.7.0

Fixed in 0.7.1

Reported by Paul Scott-Murphy, via email

failing spec in event_spec.rb

it "should uset the  timezone of dtstart when event has a duration" do
  @it = RiCal.Eve...

Fixed the regex and specs which had invalid duration times.

The PropertyValue::Duration#valid_string? is incorrect, it rejects valid duration strings and accepts others.

For example "+P1H" is an invalid duration string, ...

I wrote the attached failing spec to show what the problem is (expected 0 got 1)

Given a single event without recurrence (no rrule set). Date is before :startin...

Fixed in 0.6.3

Certain time zones have not transitions and therefore no local start time. The following spec for TZInfoTimezone tests that all TZInfo timezone identifiers can ...

Fixed in 0.6.2

context "bug report from Noboyuki Tomizawa" do

before(:each) do

  @it = RiCal.Calendar do |cal|
    cal.event do |event|
      event.description = "test"
    ...

I suspect that String.unpack is actually quicker than checking the byte with ruby, since it's a C 'primitive'

In any case I doubt that it makes much performance...

The folding which happens when exporting a calendar currently splits at a fixed character position.

This may cause a UTF-8 string with multi-byte characters to ...

Perhaps you might consider adding something to the wiki on github under FAQs

Hi Rick
Thanks for your response. The heart of my problem was that I didn't knew the Event::dtstart() function. Now I'm able to do :

> cal.first.events[1].occu...

I got one reply from the icalsify list, which indicated that I should treat any combination of /n /r as an "intentional" linebreak

RiCal is specifically designed NOT to require the tzinfo gem itself.

It will work with either the tzinfo gem or the tzinfo implementation which has been availab...

add_subcomponent fails. Could require 'tzinfo' in sample below, but that doesn't seem right.

!/us/bin/ruby

require 'rubygems'
require 'ri_cal'

timezone = <<eos
...

It appears that having timezones on EXDATEs is preventing them from excluding occurrences.

The Icalendar data in the spec below contains an exdate for each norm...

I'm not sure.

The spec says that an intentional line break should be escaped by \n or \N, but I'm unclear what is meant here by an intentional line break.

I gue...

I created #8 as a duplicate by mistake and closed it.

Failing spec

  context "bounded? bug" do
    before(:each) do
      events = RiCal.parse_string rectify_ical <<-ENDCAL
      BEGIN:VEVENT
      EXDATE:20090114...

This spec illustrates the problem

  context "bounded? bug" do

before(:each) do
  events = RiCal.parse_string rectify_ical <<-ENDCAL
  BEGIN:VEVENT
...

Here's the actual example:

    it "should properly fold on export" do
      @it.description = "Weather report looks nice, 80 degrees and partly cloudy, so foll...

Bruno,

I tried to verify your problem, but I'm not sure I understand.

It seems to work except that the second event occurences are getting DateTimes for their d...